-
Notifications
You must be signed in to change notification settings - Fork 122
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
monitoring: export collector timeout as prometheus config #1300
Merged
guggero
merged 2 commits into
lightninglabs:main
from
GeorgeTsagk:prometheus-bump-timeout
Jan 22, 2025
Merged
monitoring: export collector timeout as prometheus config #1300
guggero
merged 2 commits into
lightninglabs:main
from
GeorgeTsagk:prometheus-bump-timeout
Jan 22, 2025
+30
−9
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Pull Request Test Coverage Report for Build 12904784404Details
💛 - Coveralls |
Roasbeef
requested changes
Jan 14, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How about we make this a config option? This needs to be set with the scape timeout in mind. Otherwise, it's possible that scrapes just continue to build up if the interval is << the scrape latency.
GeorgeTsagk
force-pushed
the
prometheus-bump-timeout
branch
from
January 16, 2025 11:48
d734487
to
6c6bb3c
Compare
GeorgeTsagk
changed the title
monitoring: bump default metrics collection timeout to 120s
monitoring: export collector timeout as prometheus config
Jan 16, 2025
guggero
reviewed
Jan 16, 2025
GeorgeTsagk
force-pushed
the
prometheus-bump-timeout
branch
4 times, most recently
from
January 20, 2025 09:27
1f94bd4
to
c102640
Compare
guggero
reviewed
Jan 20, 2025
GeorgeTsagk
force-pushed
the
prometheus-bump-timeout
branch
from
January 20, 2025 13:34
c102640
to
565e4a0
Compare
guggero
approved these changes
Jan 20, 2025
GeorgeTsagk
force-pushed
the
prometheus-bump-timeout
branch
from
January 22, 2025 09:07
565e4a0
to
65679a0
Compare
ffranr
approved these changes
Jan 22, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR exports the prometheus collector timeout as a prometheus config parameter.
With this timeout we will be able to observe values on our loadtest tapds for longer periods, as the timeout will be harder to reach.